Thank you for your submission, an automated scan of your plugin code's revealed the following issues:

Required

[1][2]:You should not cast this, instead use a instanceof check to make sure that it's actually a file/folder.

Do NOT open a new PR for re-validation.
Once you have pushed all of the required changes to your repo, the bot will update the labels on this PR within 6 hours.
If you think some of the required changes are incorrect, please comment with /skip and the reason why you think the results are incorrect.

I've refactored the code to use the instanceof check to validate if the file/folder exists.

Changes requested by bot have been made, ready for additional review by human.

"fundingUrl": "https://trevortylerlee.com",
This is meant for links to services like Buy me a coffee, GitHub sponsors and so on, if you don't have such a link remove this line.

return await this.app.vault.read(templateFile);
Prefer to use Vault.cachedRead() over Vault.read() when you aren't going to be modifying the file

const leaf = this.app.workspace.getUnpinnedLeaf();
Prefer to not use deprecated APIs. Please use getLeaf(false) instead.

Is there an expected use case for the Daily Note settings and your plugin's settings to differ? For example, for the Daily Note's date format and your plugin's date format setting to be different? I would recommend either removing settings from your plugin that can be inherited from the Daily Notes plugin settings, or adding a description to each setting that defaults to the Daily Note plugin settings to make it clear that it will inherit the Daily Note plugin setting, and that the user does not need to fill out that setting.

Thanks for the feedback, made the following changes:

• use Vault.cachedRead() instead of Vault.read()
• use getLeaf(false) instead of getUnpinnedLeaf()
• remove unnecessary settings and use default Daily note settings
  • remove custom date format
  • remove custom note location
  • remove custom template

Changes requested by Zachatoo have been made, assigning additional human for additional review

Please remove the "Obsidian" branding from the image in your README, that makes it look like this is an official product.

Done.

@joethei Changes have been made, can you take another look?

Hi there, as this PR has not seen any activity in the last 30 days, it will be closed in 15 days unless there are any updates.

@joethei Bump

Hello!

I found the following issues in your plugin submission

Errors:

❌ Your latest Release is missing the main.js file.
❌ Your latest Release is missing the manifest.json file.

^{This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.}

Hello!

I found the following issues in your plugin submission

Errors:

❌ Could not parse community-plugins.json, invalid JSON. Unexpected token ']', ..."-note"
},
]
" is not valid JSON

^{This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.}

Hello!

I found the following issues in your plugin submission

Errors:

❌ Your latest Release is missing the main.js file.
❌ Your latest Release is missing the manifest.json file.

^{This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.}

@joethei can I get some help? Not sure why it's saying my latest release is missing the main.ts and manifest.json files.

@trevortylerlee The bot is correct, you are missing the main.js and manifest.json files from your latest release. Notice the difference between these two releases. If you use the GitHub action in your repo for releases then the step of adding those files to your release will be done for you.

The automated review has not found any issues with your code, ready for manual review.